Translating an external workbench/ru

Other languages:

In the following notes, "context" should be your addon's or workbench's name, for example, "MySuperAddon" or "DraftPlus", or whatever. Capitalization matters here: "Context" is not the same as "context" for example. The context makes it so that all translation of your code will be gathered under the same name, to be more easily identified by translators. That is, they will know exactly to which addon or workbench a particular string belongs.

Примечание: https://github.com/yorikvanhavre/BIM_Workbench/blob/master/utils/updateTranslations.py - универсальный скрипт, который автоматизирует весь процесс, изложенный ниже (тем не менее, чтобы понять, что делает данный скрипт, следует изучить последовательность действий изложенную далее).

Подготовка файлов исходного кода

Основная информация

In every Python .py file

import FreeCAD
translate = FreeCAD.Qt.translate

print("My text")
becomes:
print(translate("context", "My text"))
Be aware that translate() is not just a normal function: it also serves as a "tag" for the lupdate text-processing utility, so must be named exactly "translate". The lupdate program is a simple text processor, it does not execute your code. You must pass string literals directly to the translate() function: you cannot pass variables, constants, etc. For example:
# This works:
FreeCAD.Console.PrintMessage(translate("context", "My text") + "\n")

# This does not, lupdate only sees the word "a_variable", and doesn't know what that is:
a_variable = "My text"
FreeCAD.Console.PrintMessage(translate("context", a_variable ) + "\n")

# But this works -- a_variable will contain the translated string:
a_variable = translate("context", "My text")
FreeCAD.Console.PrintMessage(a_variable  + "\n")
This can be used anywhere: in print(), in FreeCAD.Console.PrintMessage(), in Qt dialogs, etc. The FreeCAD.Console functions do not automatically add the newline character (\n), so this must be added at the end if desired. This character doesn't need translation either, so it can be outside the translating function:
FreeCAD.Console.PrintMessage(translate("context", "My text") + "\n")

obj.addProperty("App::PropertyBool", "MyProperty", "PropertyGroup", QT_TRANSLATE_NOOP("App::Property", "This is what My Property does"))
Don't use your own "context" in this specific case. Keep "App::Property".

В InitGui.py

def QT_TRANSLATE_NOOP(context, text):
    return text
The QT_TRANSLATE_NOOP macro doesn't do anything, but it marks texts to be picked up by the lupdate utility later on. We only use it in special cases where FreeCAD itself takes care of everything.
self.appendMenu(QT_TRANSLATE_NOOP("Workbench", "My menu"), [list of commands, ...])
self.appendToolbar(QT_TRANSLATE_NOOP("Workbench", "My toolbar"), [list of commands, ...])

FreeCADGui.addLanguagePath("/path/to/translations")
FreeCADGui.updateLocale()
The InitGui.py file has no file attribute, so it is not easy to find the translations folder's relative location. An easy way to work around this is to make it import another file from the same folder, and in that file do:
FreeCADGui.addLanguagePath(os.path.join(os.path.dirname(__file__), "translations"))
FreeCADGui.updateLocale()

Inside each FreeCAD command class

def QT_TRANSLATE_NOOP(context, text):
    return text

def GetResources(self):
    return {'Pixmap'  : "path/to/icon.svg"),
            'MenuText': QT_TRANSLATE_NOOP("CommandName", "My Command"),
            'ToolTip' : QT_TRANSLATE_NOOP("CommandName", "Describes what the command does"),
            'Accel'   : "Shift+A"
    }
where "CommandName" is the name of the command, defined by:
FreeCADGui.addCommand('CommandName', My_Command_Class())

Gather all the strings from your module

lupdate *.ui -ts translations/uifiles.ts
This is recursive and will find .ui files inside your whole directory structure.
pylupdate *.py -ts translations/pyfiles.ts

lconvert -i translations/uifiles.ts translations/pyfiles.ts -o translations/MyModule.ts

#!/bin/sh
lupdate *.ui -ts translations/uifiles.ts
pylupdate *.py -ts translations/pyfiles.ts
lconvert -i translations/uifiles.ts translations/pyfiles.ts -o translations/MyModule.ts
rm translations/pyfiles.ts
rm translations/uifiles.ts

Send the .ts file to a translation platform

It is time to have your .ts file translated. You can choose to set up an account on a public translation platform such as Crowdin or Transifex, or you can benefit from our existing FreeCAD-addons account at Crowdin, which has many users already, and therefore more chance to have your file translated quickly and by people who know FreeCAD.

If you wish to host your file on the FreeCAD Crowdin account, get in touch with Yorik on the FreeCAD forum.

Note: some platforms like Crowdin can integrate with GitHub and do all the process from points 2, 3 and 4 automatically. For that, you can't use the FreeCAD Crowdin account; you will need to set up your own account.

Merge the translations

Once your .ts file has been translated, even if partially, you can download the translations from the site:

Компилирование переводов

Now run the lrelease program on each file that you have: 

lrelease "translations/Draft_de.ts"
lrelease "translations/Draft_fr.ts"
lrelease "translations/Draft_pt-BR.ts"

Вы можете автоматизировать процесс 

for f in translations/*_*.ts
do
    lrelease "translations/$f"
done

You should find one .qm file for each translated .ts file. The .qm files is what will be used by Qt and FreeCAD at runtime.

That's all you need. Note that certain parts of your workbench cannot be translated on-the-fly if you decide to switch languages. If this is the case, you will need to restart FreeCAD for the new language to take effect.

Тестирование переводов

  1. Switch FreeCAD to a language you have translated (for example German)
  2. Load translation into FreeCAD, ex. FreeCADGui.addTranslationPath("/path/to/the/folder/containing/qmfile")
  3. Test something, for example FreeCAD.Qt.translate("your context","some string")

Result: This should give you the German translation. If this works, then the basic setup is OK. Then we can look at something else. For example, command names should always use a special context that is the name of the command as registered to FreeCAD.

Важные заметки

Convenience script

Yorik maintains a convenience script for the BIM workbench, that can gather, upload and download ts files. You can just copy and adapt that script for your workbench:

https://github.com/yorikvanhavre/BIM_Workbench/blob/master/utils/updateTranslations.py

Technical details and advanced usage

In the above examples there are two separate functions being used: translate() and QT_TRANSLATE_NOOP. You may also run across tr() and QT_TR_NOOP, which automatically provide the "context" argument based on their calling location. These two pairs of functions are fundamentally different.

translate() and tr() accomplish two separate tasks: at runtime they perform the actual translation from the string passed into them to the final translated string. This is true whether they are provided a literal string, or a variable, or a constant: the lookup is dynamic and real-time during the run of the code. However, they provide an additional non-runtime function: they are recognized by the pylupdate utility. If (and only if) they contain a string literal, that literal is extracted by the utility. ONLY string literals are extracted by pylupdate -- if a variable is passed it is ignored by the pylupdate utility. Qt will attempt to provide a translation at runtime, but this will only work if some other piece of code called one of the translation functions with the literal string that needs to be translated, so that pylupdate can extract it. Note that the code with the string literal need not actually ever execute, it must simply exist as a line of code in a file somewhere: pylupdate performs no analysis or code execution, it is simply performing a string search and extraction.

In contrast, QT_TRANSLATE_NOOP and QT_TR_NOOP do nothing at all at runtime: they are literal "no-ops", and are completely ignored by running code. Their only use is to mark a literal string for extraction by pylupdate: it never makes sense to place a variable within a call to one of these functions, it will have no effect. They are used in circumstances where translate() or tr() will be called with a variable containing the text to translate. For example, any code that is used to create a Command or a Property will use a NOOP-type function around the command menu text or tooltip, or the property docstring: at runtime when FreeCAD displays these items to the user it calls translate(): the literal strings must have been extracted by pylupdate at the point of creation, for example: 

def GetResources(self):
    return {'Pixmap'  : "path/to/icon.svg",
            'MenuText': QT_TRANSLATE_NOOP("CommandName", "My Command"),
            'ToolTip' : QT_TRANSLATE_NOOP("CommandName", "Describes what the command does"),
            'Accel'   : "Shift+A"
    }

In this usage, at runtime the dictionary returned by this function is literally: 

{ 
    'Pixmap'  : "path/to/icon.svg",
    'MenuText': "My Command",
    'ToolTip' : "Describes what the command does",
    'Accel'   : "Shift+A"
}

There is no reference to any type of translation information. When FreeCAD actually displays this information to the user, the pseudo-code is: 

for command in commands:
    resources = command.GetResources()
    menu_text = translate(resources['MenuText'])

In this case, lupdate cannot extract any string from the call to translate() because it refers to a variable. So lupdate ignores that call, but at runtime Qt searches for the string that's passed to it. As long as someplace in the code there is a call to one of the translation functions with a matching literal string (in this case, in the GetResources() function), this translation call will succeed.

To verify that the expected strings are being extracted, you can manually run the pylupdate command: 

pylupdate myfile.py -ts outfile.ts

The file outfile.ts will contain the set of strings that are uploaded to CrowdIn for translation.

Важные ссылки

Related Pages


Документация пользователя